@JReinhold I think I'd like to verify with you something that seems to be happening here:
https://www.chromatic.com/test?appId=635781f3500dd2c49e189caf&id=637feadb2547552d19290761

When I load this story locally, the play function is ran, and the component renders as the before did in chromatic:

But it seems in chromatic the 'undefined' state is stuck, which would mean the play function did not run?

but somehow the play-function DID run on other stories, or we'd see many more stories get flagged for review.
So I'm wondering if this is some timing issue that is surfacing, or what else could be the cause?
Any ideas @JReinhold or @shilman ? 🙏

I'll see if i can add a delay to the story, perhaps chromatic doesn't understand that this is actually a story with a play function at all, therefore it doesn't wait for the play function to finish.

The special case about that story is that in itself it doesn't contain any interaction tests, but it contains a <Story /> block which references a story that does have interaction tests, which it is suppose to run because of docs.autoplay on that sub-story.

So Chromatic doesn't know there's an interaction test to run here. We should just add a delay that ensure the nested interaction test finishes.